chore(deps): update dependency npm-run-all to v4 #71
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/npm-run-all-4.x
branch
from
dfae915 to
05cdc4a
Compare
renovate
bot
force-pushed
the
renovate/npm-run-all-4.x
branch
from
05cdc4a to
6a52751
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
~3.1.2->~4.1.0Release Notes
mysticatea/npm-run-all (npm-run-all)
v4.1.5Compare Source
🐛 Bug fixes
52eaf86...1b41ac5switchedps-treepackage topidtreepackage for security reason.v4.1.4Compare Source
v4.1.3Compare Source
🐛 Bug fixes
d56c268improved label colors35f86aefixed a bug that the script name which starts with!makesnpm-run-allconfusing.v4.1.2Compare Source
Bug fixes
096779bfixed the problem that--aggregate-outputoption does not work if child tasks print large output (#111). Thank you, @jlopezxs!693261bfixed the problem that--aggregate-outputoption does not work onnpm-run-allcommand.528d105...43a6b16fixed the problem with usingyarn(#113).v4.1.1Compare Source
Bug fixes
fbd4024fixed a regression bug of--print-name.v4.1.0Compare Source
Features
e07e782add--aggregate-outputoption. This option avoids that the output of tasks is mixed even if parallel mode. Don't use this option if a task never finishes (e.g. web server, file watching, ...).Thank you, @fatso83 !
Bug fixes
f7f7b43fixed a bug thatnpm-run-allshowsMaxListenersExceededWarningwarnings if it runs many tasks in parallel.v4.0.2Compare Source
Bug fixes
b90575bfixed unintentional failing of the assertion check about--raceoption. If there is a mix of--paralleland--serialthen--raceoption had failed always. (fixes #88).v4.0.1Compare Source
Bug fixes
bb9e627fixed the problem ofnpm_execpathon Mac/Linux (#84).Thank you, @bmarcaur !
v4.0.0Compare Source
🎍 A happy new year! 🎍
Breaking changes
npm. Before, it was usingnpmcommand which is in environment variablePATH. Now, it uses the path of environment variableNPM_EXECPATH. If theNPM_EXECPATHis not defined, it uses the old way.The
NPM_EXECPATHis set by npm innpm run-scriptcommand. This implies thatnpm-run-allusesnpmwhich is running itself to run tasks.yarn.yarn runset theNPM_EXECPATHas similar tonpm run-script.Features
--max-paralleloption. You can limit the number of parallelism by this option.--npm-pathoption. You can specify the path ofnpmby this option. For example,npm-run-all foo --npm-path npmkeeps the old behavior.d7821dfadded colors for--print-labeloption. Thank you, @nulltask !Chore
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.